Post procedure care and wellness management

ABSTRACT

Systems and methods for post procedure care and wellness management. A care network for a care recipient in providing post procedure care to the care recipient for a procedure performed on the care recipient is formed. A user specific care plan for the care recipient is generated, the user specific care plan including post procedure content and first post procedure care conditions associated with the post procedure content is generated for the care recipient. Whether the first post procedure care conditions are satisfied is determined. The post procedure content is sent to the care recipient through an internal communication channel. A first care data received notification comprising a generic notification lacking any personal health information of the care recipient is sent to the care recipient through an external communication channel. The care recipient is logged in to view the post procedure content through the internal communication channel.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. Non-Provisional patentapplication Ser. No. 14/542,345, filed Nov. 14, 2014, and entitled “POSTPROCEDURE CARE AND WELLNESS MANAGEMENT,” which claims the benefit ofU.S. Provisional Patent Application Ser. No. 61/962,718, filed Nov. 14,2013, and entitled “METHOD FOR COLLECTING PROPRIETARY POPULATION HEALTHDATA THROUGH UTILIZATION OF A CLOUD-BASED AND MOBILE SERVICE BY USERS OFDIFFERING ROLLS,” which is incorporated by reference herein.

BACKGROUND

An area of ongoing research and development is post procedure caremanagement and wellness management. In particular there are problemsthat exist with implementing systems and methods that are compliant withthe health insurance portability and compliance act (hereinafterreferred to as “HIPAA”).

Other limitations of the relevant art will become apparent to those ofskill in the art upon a reading of the specification and a study of thedrawings.

SUMMARY

The following implementations and aspects thereof are described andillustrated in conjunction with systems, tools, and methods that aremeant to be exemplary and illustrative, not necessarily limiting inscope. In various implementations one or more of the above-describedproblems have been addressed, while other implementations are directedto other improvements.

Various implementations include systems and methods for post procedurecare and wellness management. In various implementations, a care networkfor a care recipient in providing post procedure care to the carerecipient for a procedure performed on the care recipient is formed.Further, in various implementations, a user specific care plan for thecare recipient, the user specific care plan including post procedurecontent and first post procedure care conditions associated with thepost procedure content is generated for the care recipient. In variousimplementations, whether the first post procedure care conditions aresatisfied is determined. In various implementations, the post procedurecontent is sent to the care recipient through an internal communicationchannel if it is determined that the first post procedure careconditions are met. Additionally, in various implementations, a firstcare data received notification is sent to the care recipient through anexternal communication channel, the first care data receivednotification being a generic notification lacking any personal healthinformation of the care recipient. In various implementations, the carerecipient is logged in to view the post procedure content through theinternal communication channel.

These and other advantages will become apparent to those skilled in therelevant art upon a reading of the following descriptions and a study ofthe several examples of the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a diagram of an example of a system for maintainingcommunication of content used in providing either or both post procedurecare and user wellness.

FIG. 2 depicts a diagram of an example of a system for managing usercredentials in providing and/or maintaining post procedure care for auser through a care network of the user.

FIG. 3 depicts a diagram of an example of a system for managing postprocedure content used in providing and/or maintaining post procedurecare.

FIG. 4 depicts a diagram of an example of a system for sending messagesinternally between users in a care network in providing and/ormaintaining post procedure care.

FIG. 5 depicts a diagram of an example of an external messaging systemfor providing and/or maintaining post procedure care for a user througha care network of the user.

FIG. 6 depicts a diagram of a post procedure analytics managementsystem.

FIG. 7 depicts a diagram of an example of a system for sending messagesinternally between users in a care network in providing and/ormaintaining post procedure care.

FIG. 8 depicts a flowchart of an example of a method for providingand/or maintaining post procedure care to a user through a care networkof the user.

FIG. 9 depicts a flowchart of an example of a method for sending caredata in a care network of a user for providing and/or maintaining postprocedure care to the user through the care network of the user.

FIG. 10 depicts a flowchart of an example of a method for generating auser specific care plan for providing and/or maintaining post procedurecare of a user through a care network of the user

FIG. 11 depicts a flowchart of an example of a method for providingand/or maintaining wellness for a user.

FIG. 12 depicts an example of a screenshot of an interface used to login to an internal communication channel.

FIG. 13 depicts an example of a screenshot of an interface for use inmanaging post procedure care of users in care networks.

FIG. 14 depicts an example of a screenshot of another example of aninterface for use in managing post procedure care of users in carenetworks

DETAILED DESCRIPTION

FIG. 1 depicts a diagram 100 of an example of a system for maintainingcommunication of content used in providing either or both post procedurecare and user wellness. The system of the example of FIG. 1 includes aunified core platform 102, a user credential management system 104, apost procedure content management system 106, an internal messagingsystem 108, an external messaging system 110, a post procedure analyticsmanagement system 112, and a user wellness management system 114.Depending upon implementation-specific or other considerations, one or acombination of the unified core platform 102, the user credentialmanagement system 104, the post procedure content management system 106,the internal messaging system 108, the external messaging system 110,the post procedure analytics management system 112, and the userwellness management system 114 can be integrated or implement proceduresin compliance with HIPAA standards.

The unified core platform functions to couple the user credentialmanagement system 104, the post procedure content management system 106,the internal messaging system 108, the external messaging system 110,the post procedure analytics management system 112, and the userwellness management system 114. In coupling the user credentialmanagement system 104, the post procedure content management system 106,the internal messaging system 108, the external messaging system 110,the post procedure analytics management system 112, the wellnessmanagement system 114 to each other, the unified core platform canexchange data and/or distribute functions used in maintainingcommunication of content used in providing either or both post procedurecare and user wellness. The unified core platform 102 can be implementedas a computer-readable medium or part of a computer-readable medium. Asused in this paper, a “computer-readable medium” is intended to includeall mediums that are statutory (e.g., in the United States, under 35U.S.C. 101), and to specifically exclude all mediums that arenon-statutory in nature to the extent that the exclusion is necessaryfor a claim that includes the computer-readable medium to be valid.Known statutory computer-readable mediums include hardware (e.g.,registers, random access memory (RAM), non-volatile (NV) storage, toname a few), but may or may not be limited to hardware.

A computer-readable medium, as is used in this paper, is intended torepresent a variety of potentially applicable technologies. For example,a computer-readable medium can be used to form a network or part of anetwork. Where two components are co-located on a device, thecomputer-readable medium 102 can include a bus or other data conduit orplane. Where a first component is co-located on one device and a secondcomponent is located on a different device, a computer-readable mediumcan include a wireless or wired back-end network or LAN. Acomputer-readable medium can also encompass a relevant portion of a WANor other network, if applicable.

The unified core platform 102, the user credential management system104, the post procedure content management system 106, the internalmessaging system 108, the external messaging system 110, the postprocedures analytics management system 112, the user wellness managementsystem 114, and other applicable systems, or devices described in thispaper can be implemented as a computer system, a plurality of computersystems, or parts of a computer system or a plurality of computersystems. A computer system, as used in this paper, is intended to beconstrued broadly. In general, a computer system will include aprocessor, memory, non-volatile storage, and an interface. A typicalcomputer system will usually include at least a processor, memory, and adevice (e.g., a bus) coupling the memory to the processor. The processorcan be, for example, a specific-purpose central processing unit (CPU),such as a microprocessor, or a special-purpose processor, such as amicrocontroller.

The memory can include, by way of example but not limitation, randomaccess memory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM).The memory can be local, remote, or distributed. The bus can also couplethe processor to non-volatile storage. The non-volatile storage is oftena magnetic floppy or hard disk, a magnetic-optical disk, an opticaldisk, a read-only memory (ROM), such as a CD-ROM, EPROM, or EEPROM, amagnetic or optical card, or another form of storage for large amountsof data. Some of this data is often written, by a direct memory accessprocess, into memory during execution of software on the computersystem. The non-volatile storage can be local, remote, or distributed.The non-volatile storage is optional because systems can be created withall applicable data available in memory.

Software is typically stored in the non-volatile storage. Indeed, forlarge programs, it may not even be possible to store the entire programin the memory. Nevertheless, it should be understood that for softwareto run, if necessary, it is moved to a computer-readable locationappropriate for processing, and for illustrative purposes, that locationis referred to as the memory in this paper. Even when software is movedto the memory for execution, the processor will typically make use ofhardware registers to store values associated with the software, andlocal cache that, ideally, serves to speed up execution. As used herein,a software program is assumed to be stored at an applicable known orconvenient location (from non-volatile storage to hardware registers)when the software program is referred to as “implemented in acomputer-readable storage medium.” A processor is considered to be“configured to execute a program” when at least one value associatedwith the program is stored in a register readable by the processor.

In one example of operation, a computer system can be controlled byoperating system software, which is a software program that includes afile management system, such as a disk operating system. One example ofoperating system software with associated file management systemsoftware is the family of operating systems known as Windows® fromMicrosoft Corporation of Redmond, Wash., and their associated filemanagement systems. Another example of operating system software withits associated file management system software is the Linux operatingsystem and its associated file management system. The file managementsystem is typically stored in the non-volatile storage and causes theprocessor to execute the various acts required by the operating systemto input and output data and to store data in the memory, includingstoring files on the non-volatile storage.

The bus can also couple the processor to the interface. The interfacecan include one or more input and/or output (I/O) devices. The I/Odevices can include, by way of example but not limitation, a keyboard, amouse or other pointing device, disk drives, printers, a scanner, andother I/O devices, including a display device. The display device caninclude, by way of example but not limitation, a cathode ray tube (CRT),liquid crystal display (LCD), or some other applicable known orconvenient display device. The interface can include one or more of amodem or network interface. It will be appreciated that a modem ornetwork interface can be considered to be part of the computer system.The interface can include an analog modem, isdn modem, cable modem,token ring interface, satellite transmission interface (e.g. “directPC”), or other interfaces for coupling a computer system to othercomputer systems. Interfaces enable computer systems and other devicesto be coupled together in a network.

The computer systems can be compatible with or implemented as part of orthrough a cloud-based computing system. As used in this paper, acloud-based computing system is a system that provides virtualizedcomputing resources, software and/or information to client devices. Thecomputing resources, software and/or information can be virtualized bymaintaining centralized services and resources that the edge devices canaccess over a communication interface, such as a network. “Cloud” may bea marketing term and for the purposes of this paper can include any ofthe networks described herein. The cloud-based computing system caninvolve a subscription for services or use a utility pricing model.Users can access the protocols of the cloud-based computing systemthrough a web browser or other container application located on theirclient device.

A computer system can be implemented as an engine, as part of an engine,or through multiple engines. As used in this paper, an engine includesat least two components: 1) a dedicated or shared processor and 2)hardware, firmware, and/or software modules that are executed by theprocessor. Depending upon implementation-specific or otherconsiderations, an engine can be centralized or its functionalitydistributed. An engine can include special purpose hardware, firmware,or software embodied in a computer-readable medium for execution by theprocessor. The processor transforms data into new data using implementeddata structures and methods, such as is described with reference to theFIGs. in this paper.

The engines described in this paper, or the engines through which thesystems and devices described in this paper can be implemented, can becloud-based engines. As used in this paper, a cloud-based engine is anengine that can run applications and/or functionalities using acloud-based computing system. All or portions of the applications and/orfunctionalities can be distributed across multiple computing devices,and need not be restricted to only one computing device. In someembodiments, the cloud-based engines can execute functionalities and/ormodules that end users access through a web browser or containerapplication without having the functionalities and/or modules installedlocally on the end-users' computing devices.

As used in this paper, datastores are intended to include repositorieshaving any applicable organization of data, including tables,comma-separated values (CSV) files, traditional databases (e.g., SQL),or other applicable known or convenient organizational formats.Datastores can be implemented, for example, as software embodied in aphysical computer-readable medium on a general- or specific-purposemachine, in firmware, in hardware, in a combination thereof, or in anapplicable known or convenient device or system. Datastore-associatedcomponents, such as database interfaces, can be considered “part of” adatastore, part of some other system component, or a combinationthereof, though the physical location and other characteristics ofdatastore-associated components is not critical for an understanding ofthe techniques described in this paper.

Datastores can include data structures. As used in this paper, a datastructure is associated with a particular way of storing and organizingdata in a computer so that it can be used efficiently within a givencontext. Data structures are generally based on the ability of acomputer to fetch and store data at any place in its memory, specifiedby an address, a bit string that can be itself stored in memory andmanipulated by the program. Thus, some data structures are based oncomputing the addresses of data items with arithmetic operations; whileother data structures are based on storing addresses of data itemswithin the structure itself. Many data structures use both principles,sometimes combined in non-trivial ways. The implementation of a datastructure usually entails writing a set of procedures that create andmanipulate instances of that structure. The datastores, described inthis paper, can be cloud-based datastores. A cloud-based datastore is adatastore that is compatible with cloud-based computing systems andengines.

In a specific implementation, the user credential management system 104functions to manage user credentials for authenticating users inaccessing one or a combination of the systems and or engines describedin this paper. Depending upon implementation-specific or otherconsiderations, user credentials can include a user identification, auser name, a user password, and/or a user token. In managing usercredentials, the user credential management system 104 can receiveand/or identify user credentials used for providing a user access.Further, in managing user credentials, the user credential managementsystem 104 can verify whether provided user credentials match usercredentials for providing a user access.

In a specific implementation, the user credential management system 104functions to manage a care network for an individual. A care network, asused in this paper, includes a network of care providers or users thatare selected by a user for providing and/or maintaining either or bothpost procedure care to a user or wellness for a user, who is a carerecipient. Depending upon implementation-specific or otherconsiderations, a care network can be a private network of users who cancommunicate with each other or select users who are within the carenetwork. For example, a care network can include a doctor who performs aprocedure on a patient and family members of the patient who providecare to the patient after the procedure is performed. Further dependingupon implementation-specific or other considerations, users and/or careproviders within a care network can communicate, or otherwise sendand/or receive data privately through an applicable system fortransmitting data between individuals within the care network, such asthe internal messaging systems described in this paper. In communicatingprivately, only specific people can send and receive data between eachother, for example only individuals within a care network and/orspecific individuals within a care network can send and receive caredata between each other for a given instance of the care network.

In a specific implementation, a procedure, for which post procedure careis provided and/or maintained includes a medical procedure provided to auser. For example, a procedure can include a surgery performed on auser. In another example, a procedure can include a long-term careprocedure performed on a user, such as monitoring the user's cholesterollevels. Depending upon implementation-specific or other considerations,a time during which post procedure care is provided can include the timeimmediately following a performance of a procedure on a user, the timeafter a user is discharged from a hospital or an appropriate medicalcare technician after performance of a procedure on the user, and/or thetime during which one or a plurality of procedures are performed on auser.

In a specific implementation, the post procedure content managementsystem 106 functions to manage post procedure content used in providingand maintaining post procedure care to a user. As used in this paper,post procedure content includes data that is sent to at least one userin a care network in providing and/or maintaining post procedure care toa user. Depending upon implementation-specific or other considerations,post procedure content can include care alerts. Care alerts can includereminders of tasks a user needs to perform in providing and maintainingpost procedure care. For example, a care alert can be a reminder that auser needs to take a measurement of their blood pressure. In anotherexample, a care alert can be a reminder that a care provider needs toadminister medication to a patient. Further depending uponimplementation-specific or other considerations, post procedure contentcan include suggested media used to aid a user in recovering from aprocedure. For example, if a user has a procedure performed on them forfixing a broken leg, then post procedure content can include imagesand/or videos of rehabilitation exercises for the broken leg. Dependingupon implementation-specific or other considerations, post procedurecontent can include content used to engage and/or gauge the progress ofa user in post procedure care. For example, if a procedure is performedon a user for fixing a broken leg, then post procedure content caninclude questions assessing a degree to which the user has healed afterthe procedure. Further depending upon implementation-specific or otherconsiderations, post procedure content can include requests for datafrom a user in managing post procedure care. For example, post procedurecontent can include a request for a blood pressure reading of a user.The post procedure content management system 106 can collect postprocedure content from users within a care network, e.g. a doctor whoperformed a procedure, templates of standard post procedure contentpresented to users who undergo a specific procedure, and/or third partysources who provide post procedure content.

In a specific implementation, the post procedure content managementsystem 106 functions to determine post procedure care conditions used inproviding and/or maintaining post procedure care to a user. A postprocedure care condition, as is used in this paper, includes a conditionfor sending post procedure content to a user and which users to sendport procedure content within a care network in providing and/ormaintaining post procedure care. Depending upon implementation-specificor other considerations, a post procedure care condition can specify tosend post procedure content to a user after a specific amount of time.For example, a post procedure care condition can specify to send postprocedure content after two weeks have passed since the procedure wasperformed on a user. Further depending upon implementation-specific orother considerations, a post procedure care condition can specify tosend post procedure content if a certain occurrence is not met. Forexample, a post procedure care condition can specify to send a reminderfor a blood pressure reading if a blood pressure reading is not receivedwithin a certain amount of time. Depending upon implementation-specificor other considerations, a post procedure care condition can specify tosend post procedure content if a certain event occurs. For example, apost procedure care condition can specify to send a notice to a caregiver if a user's weight is above a predetermined amount.

In a specific implementation, in managing post procedure content, thepost procedure content management system 106 can manage a care plan fora user. A care plan for a user can include post procedure content thatcan be sent to a user and post procedure care conditions that identifywhether the post procedure content should be sent to the user. Dependingupon implementation-specific or other considerations, in managing a careplan for a user, the post procedure content management system 106 caneither or both generate and update the care plan for the user.

In a specific implementation, the internal messaging system 108functions to transmit data through internal communication channels tousers within a care network for either or both providing post procedurecare to a user and wellness to the user. Internal communication channelsinclude communication channels in which a user must login to view datasent through the internal communication channels and send data throughthe internal communication channels. In transmitting data to userswithin a care network, the internal messaging system 108 can transmitpost procedure content to the users within the care network. Further, intransmitting data to users within a care network, the internal messagingsystem 108 can determine whether post procedure care conditions are metand subsequently transmit post procedure content according to the postprocedure care conditions. Depending upon implementation-specific orother considerations, the internal messaging system 108 can directlytransmit post procedure content to an account associated with a userand/or publish post procedure content on a feed through which one or aplurality of users within a care network can view the published postprocedure content. In directly transmitting post procedure content to anaccount associated with a user, the internal messaging system 108 canprovide peer-to-peer chat or group chat functioning. Further dependingupon implementation-specific or other considerations, a user has tologin using their credentials through the user credential managementsystem 104 in order to view post procedure content transmitted to eitherthem or published on a feed. As a result of requiring a user to login totheir account to view transmitted post procedure content, the internalmessaging system 108 is compliant with HIPAA standards.

In a specific implementation, the internal messaging system 108functions to receive care data from users within a care network andtransmit received care data to users within the care network. Care datacan include post procedure content, data related to care of a patient,and or data generated in response to post procedure content. Forexample, care data can include a video that a doctor wants their patientto view. In another example, care data can include measured vitalstatistics of a patient, as taken by a care giver for the patient inresponse to a care alert requesting that the vital statistics of thepatient be taken. Care data can have associated post procedure careconditions that dictate whether the care data can be transmitted and/orpublished, and which users to send the care data to or are allowed toaccess the care data. Depending upon implementation-specific or otherconsiderations, the internal messaging system 108 can directly transmitcare data to an account associated with a user and/or publish care dataon a feed through which one or a plurality of users within a carenetwork can view the care content.

In a specific implementation, the internal messaging system 108 canreceive care data from a device of a user, an application, and/or aservice. Depending upon implementation-specific or other considerations,the internal messaging system 108 can receive care data from a wearabledevice of a user. Examples of wearable devices include Basis Band®, BodyMedia Cora®, Body Media Link®, Fitbit Flex®, Fitbit Force®, Fitbit One®,Jawbone UP®, Jawbone UP24®, Nike Fuel Band®, Fitbug Orb®, Fitbug Air®,Fitbug Go®, Withings Pulse®, Pebble Original®, Pebble Steel®, iHealthActivity Tracker®, Lumoback®, Omron®, and iHeart Omron®. Example ofdevices of a user include computers, smart phones, laptops, Fitbit AriaScale®, Fitbug WoW Scale®, Withings Scale®, Glooko®, iHealth BloodGlucose Monitor®, iHealth BP Monitor®, Withings BP Monitor®, iHealthPulse Oximeter®, and Vitadock®. Example of application from which theinternal messaging system 108 can receive care data from includeDailymile®, Mapmyfitness®, Moves App®, RunKeeper®, Strava®, ManageBGL®,Fatsecret®, and Fleetly®.

In a specific implementation, the external messaging system 110functions to send care data received notifications to users within acare network through communication channels external from internalcommunication channels used by the internal message system 108.Communication channels external from the internal message system 108 caninclude an applicable communication channel separate from an internalcommunication channel used by the internal messaging system 108.Examples of communication channels external from the internal messagesystem include email supported by third parties and short messageservice (hereinafter referred to as “SMS”). The external messagingsystem 110 can send a notification, e.g. a push notification, to a userwithin a care network over a communication channel external from theinternal messaging system 108 when a user receives either or both postprocedure content and care data through the internal messaging system108. For example, if a doctor receives care data including vitalstatistics of a patient through the internal messaging system 108, thenthe external messaging system 110 can send a notification to the doctorindicating that the doctor has received care data. Care data receivednotification sent by the external messaging system 110 can be generic inthat they do not contain any protected health information of userswithin a care network and only notify a user that they have receivedcare data through the internal messaging system 108. For example, a caredata received notification sent to a user by the external messagingsystem can indicate only that care data and/or post procedure contenthas been received by an account of the user, and not include anythingincluded in the received care and/or post procedure content. As aresult, in sending care data received notifications that are generic,the external messaging system 110 can be compliant with HIPAA standards.

In a specific implementation, the post procedure analytics managementsystem 112 functions to generate analytics reports for data sent withina care network for providing and/or maintaining post procedure care.Depending upon implementation-specific or other considerations, the postprocedure analytics management system 112 can generate analytics reportsfor post procedure care based on either or both post procedure contentand care data sent within a care network.

In a specific implementation, the user wellness management system 114functions to provide and/or maintain wellness for a user. In providingand/or maintaining wellness for a user the user wellness managementsystem 114 can manage a wellness network of a user. Users within awellness network of a user can communicate using the internal messagingsystem 108. Further, in providing and/or maintaining wellness for auser, the user wellness management system 114 can perform a health riskassessment and log activities of a user for maintaining or increasingwellness of the user. Additionally, the user wellness management system114 can present challenge to a user that if performed, improve thewellness of the user.

FIG. 2 depicts a diagram 200 of an example of a system for managing usercredentials in providing and/or maintaining post procedure care for auser through a care network of the user. The example system shown inFIG. 2, includes a computer-readable medium 202, user devices 204-1 . .. 204-n (hereinafter referred to as “user devices 204”), and a usercredential management system 206. In the example system shown in FIG. 2,the user devices 204 and the user credential management system 206 arecoupled to each other through the computer-readable medium 202.

In a specific implementation, the user devices 204 functions accordingto applicable devices of a user for sending and receiving data used inproviding and/or maintaining post procedure care for a user through acare network of the user. The user devices 204 can be associated with auser who is the subject of a care network, and/or users within the carenetwork of the user. The user devices 204 can be used to send usercredentials and/or receive care network enrollment requests by a user.Care network enrollment requests include requests for a user to accept arequest to join a care network and/or provide credentials for enrollingto join a care network. For example, if a patient wishes to add familymembers to a care network, then user devices 204 of the family memberscan be used to receive care network enrollment requests by the familymembers. Depending upon implementation-specific or other considerations,the user devices 204 can be thin client devices or ultra-thin clientdevices. Further depending upon implementation-specific or otherconsiderations, the user devices 204 can include wireless or cellularnetwork interfaces through which the user devices 204 can be wirelesslyconnected to the computer-readable medium 202.

In a specific implementation, the user credential management system 206functions according to an applicable system for managing usercredentials in providing and/or maintaining post procedure care to auser through a care network of the user, such as the user credentialmanagement systems described in this paper. In managing usercredentials, the user credential management system can receive and/orassign user credentials for logging a user in to view and or transmitdata through an applicable system for internally transmitting data usedin providing and/or maintain post procedure care of a user through acare network of the user, such as the internal messaging systemsdescribed in this paper. Further, in managing user credentials, the usercredential management system 206 can send enrollment requests to usersfor enrolling and/or joining a care network. In managing usercredentials, the user credential management system 206 can log in a userfor viewing and or transmitting data used in providing and/ormaintaining post procedure care by receiving user credentials from auser and authenticating the user credentials.

In a specific implementation, the user credential management system 206functions to manage a care network of a user. In managing a care networkof a user, the user credential management system 206 can add, update,and/or remove users from the care network of the user. Depending uponimplementation-specific or other considerations, the user credentialmanagement system 206 can add, update, and/or remove users from the carenetwork of a user based on instructions received from the user. Forexample, a user can send instructions specifying to add a family memberto a care network, and the user credential management system 206 can addthe family member to the care network. In managing a care network basedon instructions from a user that the care network is created for, theuser credential management system 206 functions in compliance with HIPAAstandards. Further depending upon implementation-specific or otherconsiderations, the user credential management system 206 can suggestusers to add to a care network. For example, if a doctor performed aprocedure patient, then the user credential management system 206 cansuggest to the user that the doctor be included in the care network ofthe patient. In managing a care network of a user, the user credentialmanagement system 206 can require that the user login using theircredentials in providing security and compliance with HIPAA standards.Further in managing a care network of a user, the user credentialmanagement system 206 can send enrollment requests to users added to acare network.

In the example system shown in FIG. 2, the user credential managementsystem 206 includes a user credentials management engine 208, a usercredentials datastore 210, a user login engine 212, a post procedurecare network management engine 214, and a care network datastore 216. Ina specific implementation, the user credentials management enginefunctions to manage user credentials for logging a user in to view andor transmit data through an applicable system for internallytransmitting data used in providing and/or maintain post procedure careof a user through a care network of the user, such as the internalmessaging systems described in this paper. In managing user credentials,the user credential management engine 208 can assign user credentials toa user for registering a user. For example, if a patient is using thesystem for the first time to set up a care network for providing andmaintaining post procedure care, then the user credentials managementengine 208 can assign user credentials to the user. Depending uponimplementation-specific or other considerations, in assigning usercredentials to a user, the user credentials management engine 208 canprovide an access token and or certificates to user devices 204 of theuser for logging in the user.

In a specific implementation, the user credential datastore 210functions to store user credentials assigned to a user by the usercredentials management engine 208. User credentials stored in the usercredentials datastore 210 can be used to authenticate a user inaccessing an internal messaging system for viewing and/or sending caredata used in providing and/or maintaining post procedure care for a userthrough a care network of the user. User credentials stored in the usercredentials datastore 210 can be stored as encrypted data at the filelevel, as in compliance with HIPAA standards. Further in compliance withHIPAA standards, the user credential datastore 210 can be accessiblethrough at least two factor authentication. For example, the usercredential datastore 210 can be accessed through a secure socket layervirtual private network (hereinafter referred to as “SSL VPN”)implementing at least two factor authentication.

In a specific implementation, the user login engine 212 functions to login a user for access to an internal messaging system for viewing and/orsending care data in providing post procedure care to a user through acare network of the user. In logging in a user for access to an internalmessaging system, the user login engine 212 can receive user credentialsof a user from the user devices 204 of the user when the user attemptsto log in for accessing the internal messaging system. Further, inlogging in a user for access to an internal messaging system, the userlogin engine 212 can compare received user credentials of a user withuser credentials of the user stored in the user credentials datastore210 in order to authenticate the user. If the user is authenticated, theuser login engine 212 can provide the user with access to an internalmessaging system for viewing and/or sending care data in providing postprocedure care to a user through a care network of the user.

In a specific implementation, the user login engine 212 functions tologout a user from access to an internal messaging system for viewingand/or sending care data in providing post procedure care to a userthrough a care network of the user. In logging out a user from access toan internal messaging system, the user login engine 212 can determinewhether a user is inactive in interacting with internal messaging systemand determining an amount of time that the user has remain inactive. Theuser login engine 212 can determine to logout a user from accessing aninternal messaging system if the user has remained inactive with theinternal messaging system for a specific amount of time. For example,the user login engine 212 can logout a user from accessing an internalmessaging system if the user has remained inactive with the internalmessaging system for 5 or more minutes. In logging out a user fromaccessing an internal messaging system for viewing and/or sending caredata in providing post procedure care to a user through a care networkof the user, the user login engine 212 is in compliance with HIPAAstandards.

In a specific implementation, the post procedure care network managementengine 214 functions to manage a care network of a user. In managing acare network of a user, the post procedure care network managementengine 214 can add, update, and/or delete users from a care network of auser. The post procedure care network management engine 214 can manage acare network of a user based on instructions received from the user.Instructions received from a user can include whether to add or delete auser from a care network, and/or what care data the user in the carenetwork can view and/or transmit. For example, if the user sendsinstructions to add a family member to their care network, then the postprocedure care network management engine 214 can add the family memberto the care network. In another example, if the user sends instructionsto remove a family member from their care network, then the postprocedure care network management engine 214 can remove the familymember from the care network.

Depending upon implementation-specific or other considerations, the postprocedure care network management engine 214 can suggest users to add toa care network. For example if a doctor performed a procedure on apatient, then the post procedure care network management engine 214 cansuggest a user to add to a care network. Data used in managing a carenetwork, including either or both instructions used in managing a carenetwork of a user, and suggested users for the care network, can be sentbetween the post procedure care network management engine 214 and userdevices 204 of a user through either or both applicable internalmessaging systems and external messaging systems, such as the internaland external messaging systems described in this paper.

In a specific implementation, the care network datastore 216 functionsto store care network data describing a care network of a user asmanaged by the post procedure care network management engine 214. Carenetwork data can include an identification of users within a carenetwork, what care data can be sent to which users within the carenetwork in accordance with satisfaction of post procedure careconditions for the care data, and/or external communication channelsthrough which users can receive data outside of an internal messagingsystem. Care network data stored in the care network datastore 216 canbe generated by the post procedure care network management engine 214 inconjunction with the management of a care network. For example if a useris added to a care network, then the post procedure care networkmanagement engine 214 can modify care network data stored in the carenetwork datastore 216 to identify the user added to the care networkand/or what care data can be sent to the user in accordance withsatisfaction of post procedure care conditions for the care data. Carenetwork data stored in the care network datastore 216 can be stored asencrypted data at the file level, as in compliance with HIPAA standards.Further in compliance with HIPAA standards, the care network datastore216 can be accessible through at least two factor authentication. Forexample, the care network datastore 216 can be accessed through an SSLVPN implementing at least two factor authentication.

In a specific implementation, the user credentials management engine 208can manage user credentials based on managing of a care network by thepost procedure care network management engine 214. In managing usercredentials based on managing of a care network by the post procedurecare network management engine 214, the user credentials managementengine can send enrollment requests to users who are added to a carenetwork by the post procedure care network management engine 214. Forexample, if a patient adds a family member to a care network, then theuser credentials management engine 208 can send an enrollment request tothe family member. Depending upon implementation-specific or otherconsiderations, the user credential management engine 208 can assignuser credentials to a user that the user can utilize in accessing aninternal messaging system for viewing and/or sending care data forproviding post procedure care to the user through a care network of theuser. In managing user credentials based on managing of a care networkby the post procedure care network management engine 214, the usercredentials management engine 208 can update user credentials in theuser credentials datastore 210. For example, if a user is added to acare network and the user credentials management engine 208 assigns usercredentials to the user, then the user credentials management engine 208can update the user credentials in the user credentials datastore 210 toinclude the assigned credentials. In another example, if a user isremoved from a care network, then the user credentials management engine208 can update the user credentials in the user credentials datastore210 to delete the user credentials of the removed user.

In an example of operation of the example system shown in FIG. 2, theuser credentials management engine 208 assigns user credentials to apatient are utilized in accessing an internal messaging system forviewing and/or sending care data for providing post procedure care tothe user through a care network of the user. In the example of operationof the example system shown in FIG. 2, the user credentials managementengine 208 updates user credentials in the user credentials datastore210 to indicate user credentials assigned to the patient. Further, inthe example of operation of the example system shown in FIG. 2, the userlogin engine 212 receives user credentials from the patient and logs inthe patient based on the received user credentials. In the example ofoperation of the example system shown in FIG. 2, the post procedure carenetwork management engine 214 functions to add a user to a care networkof the patient based on instructions received from the patient.Additionally, in the example of operations of the example system shownin FIG. 2, the post procedure care network management engine 214 updatescare network data stored in the care network datastore 216 to indicatethat the user is part of the care network of the patient. In the exampleof operation of the example system shown in FIG. 2, the user credentialmanagement engine 208 sends an enrollment request to the user andassigns user credentials to the user. Further, in the example ofoperation, the user login engine 212 receives user credentials from theuser and logs in the user with the received user credentials.

FIG. 3 depicts a diagram 300 of an example of a system for managing postprocedure content used in providing and/or maintaining post procedurecare. The example system shown in FIG. 3 includes a computer-readablemedium 302, user devices 304-1 . . . 304-n (hereinafter referred to as“user devices 304”), and a post procedure content management system 306.In the example system shown in FIG. 3, the user devices 304 and the postprocedure content management system 306 are coupled to each otherthrough the computer-readable medium 302.

In a specific implementation, the user devices 304 function according toan applicable user device for sending and/or receiving data used inproviding and/or maintaining post procedure care to a user through acare network of the user, such as the user devices described in thispaper. The user devices 304 can be associated with a user who is thesubject of a care network, and/or users within the care network of theuser. The user devices 304 can be used to send care data including carecontent and post procedure care conditions for generating a userspecific care plan. Depending upon implementation-specific or otherconsiderations, the user devices 304 can be thin client devices orultra-thin client devices. Further depending uponimplementation-specific or other considerations, the user devices 304can include wireless or cellular network interfaces through which theuser devices 304 can be wirelessly connected to the computer-readablemedium 302.

In a specific implementation, the post procedure content managementsystem 306 functions to manage post procedure content used in providingand/or maintaining post procedure care for a user through a care networkof the user. In managing post procedure content, the post procedurecontent management system 306 can retrieve care data including postprocedure content and post procedure care conditions from either or bothusers within a care network and third party sources. For example, thepost procedure content management system 308 can retrieve post procedurefrom a third party who provides standard care procedures. In anotherexample, the post procedure content management system 308 can retrievepost procedure content and/or post procedure content conditions from adoctor who performed a procedure on a patient. Further, in managing postprocedure content, the post procedure content management system 306 cangenerate a customizable care plan template. A customizable care plantemplate can include a template of a care plan that can be customized bya user, including either or both a care provider or a doctor whoperformed a procedure, to create a user specific care plan for a userupon whom a procedure was performed. The post procedure contentmanagement system can send a customizable care plan template to a userassociated with the user devices 304. Additionally, the post procedurecontent management system can receive customized care plan data from auser within a care network. Customized care plan data can include postprocedure content and/or post procedure care conditions generated eitheror both with the aid of a customizable care plan template and withoutthe aid of a customizable care plan template. The post procedure contentmanagement system 306 can generate a user specific care plan fromreceived customized care plan data.

In the example system shown in FIG. 3, the post procedure contentmanagement system includes a care content retrieval engine 310, acustomizable care plan template management engine 312, a customizablecare plan template datastore 314, a user specific care plan managementengine 316, and a user specific care plan datastore 318. In a specificimplementation, the care content retrieval engine 310 functions toretrieve care data, including post procedure content and/or postprocedure care conditions. Depending upon implementation-specific orother considerations, the care content retrieval engine 310 can retrievecare data from either or both a third party source or users within acare network. For example, the care content retrieval engine 310 canretrieve care data from a third party source that provides standards forpost procedure care. In another example, the care content retrievalengine 310 can retrieve care data from a doctor who performed aprocedure on a patient.

In a specific implementation, the customizable care plan templatemanagement engine 312 functions to manage customizable care plantemplates. In managing customizable care plan templates, thecustomizable care plan template management engine 312 can generate acustomizable care plan template. Depending upon implementation-specificor other considerations, a customizable care plan template generated bythe customizable care plan template management engine 312 can bespecific to a type of procedure performed, a doctor who performs aprocedure, and/or a caregiver. The customizable care plan templatemanagement engine 312 can generate a customized care plan template fromcare data retrieved by the care content retrieval engine 310. Forexample, the customizable care plan template management engine 312 cangenerate a customizable care plan template from care data retrieved froma third party source who provides standard care practices for a specificprocedure. Further, in managing customizable care plan templates, thecustomizable care plan template management engine 312 can send acustomizable care plan template to one or a plurality of users within acare network. For example, the customizable care plan templatemanagement engine 312 can send a customizable care plan template to adoctor who performed a procedure.

In a specific implementation, the customizable care plan templatedatastore 314 functions to store a customizable care plan. Thecustomizable care plan template datastore 314 can store a customizablecare plan template created by the customizable care plan templatemanagement engine 312. In sending a customizable care plan template toone or a plurality of user, the customizable care plan templatemanagement engine 312 can retrieve the customizable care plan templatefrom the customizable care plan template datastore 314.

In a specific implementation, the user specific care plan managementengine 316 functions to manage a user specific care plan for a user uponwhom a procedure is performed. In managing a user specific care plan,the user specific care plan management engine 316 can generate a userspecific care plan for a user. Depending upon implementation-specific orother considerations, the user specific care plan management engine 316can generate a user specific care plan from received customized careplan data. Customized care plan data can be received, by the userspecific care plan management engine 316, from a user within a carenetwork in response to either a customizable care plan template ordirectly from a user without the aid of a customizable care plantemplate. Further depending upon implementation-specific or otherconsiderations, the user specific care plan management engine 316 cangenerate a user specific care plan from care data retrieved by the carecontent retrieval engine 310.

In a specific implementation, the user specific care plan datastore 318functions to store user specific care plan data. User specific care plandata includes data indicating a care plan for a user. User specific careplan data stored in the user specific care plan datastore 318 canindicate a user specific care plan for a user, as generated by the userspecific care plan management engine 316. User specific care plan datastored in the user specific care plan datastore 318 can be stored asencrypted data at the file level, as in compliance with HIPAA standards.Further in compliance with HIPAA standards, the user specific care plandatastore 318 can be accessible through at least two factorauthentication. For example, the user specific care plan datastore 318can be accessed through an SSL VPN implementing at least two factorauthentication.

In an example of operation of the example system shown in FIG. 3, thecare content retrieval engine 310 retrieves care data. In the example ofoperation of the example system shown in FIG. 3, the customizable careplan template management engine 312 generates a customizable care plantemplate using, at least in part, the retrieved care data. Further, inthe example of operation of the example system shown in FIG. 3, thecustomizable care plan template management engine 312 sends thecustomizable care plan template to a doctor within a care network. Inthe example of operation of the example system shown in FIG. 3, the userspecific care plan management engine 316 receives customized care plandata from the doctor. Additionally, in the example of operation of theexample system shown in FIG. 3, the user specific care plan managementengine 316 generates a user specific care plan based on the receivedcustomized care plan data.

FIG. 4 depicts a diagram 400 of an example of a system for sendingmessages internally between users in a care network in providing and/ormaintaining post procedure care. The example system shown in FIG. 4includes a computer-readable medium 402, user devices 404-1 . . . 404-n(hereinafter referred to as “user devices 404”), a care networkdatastore 406, a user specific care plan datastore 408, and an internalmessaging system 410. In the example system shown in FIG. 4, the userdevices 404, the care network datastore 406, the user specific care plandatastore 408, and the internal messaging system 410 are coupled to eachother through the computer-readable medium 402.

In a specific implementation, the user devices 404 function according toan applicable user device for sending and/or receiving data used inproviding and/or maintaining post procedure care to a user through acare network of the user, such as the user devices described in thispaper. The user devices 404 can be associated with a user who is thesubject of a care network, and/or users within the care network of theuser. The user devices 404 can be used to send and receive care dataincluding care content and data generated in response to care data.Depending upon implementation-specific or other considerations, the userdevices 404 can include applications that allow users to send andreceive data for viewing care data and generating and sending care datathrough an internal messaging system. Depending uponimplementation-specific or other considerations, the user devices 404can be thin client devices or ultra-thin client devices. Furtherdepending upon implementation-specific or other considerations, the userdevices 404 can include wireless or cellular network interfaces throughwhich the user devices 404 can be wirelessly connected to thecomputer-readable medium 402.

In a specific implementation, the care network datastore 406 functionsaccording to an applicable datastore for storing care network data, suchas the care network datastores described in this paper. Care networkdata stored in the care network datastore 406 can include data about acare network of a specific user. Depending upon implementation-specificor other considerations, care network data stored in the care networkdatastore 406 can include an identification of users within a carenetwork, what care data can be sent to which users within the carenetwork in accordance with satisfaction of post procedure careconditions for the care data, and/or external communication channelsthrough which users can receive data.

In a specific implementation, the user specific care plan datastore 408functions according to an applicable datastore for storing user specificcare plan data, such as the user specific care plan datastores describedin this paper. The user specific care plan datastore 408 can store userspecific care plan data indicating a care plan for a user. User specificcare plan data stored in the user specific care plan datastore 408 caninclude post procedure content that can be sent to users within a carenetwork, and post procedure care conditions associated with sending thepost procedure content.

In a specific implementation, the internal messaging system 410functions according to an applicable system for transmitting datathrough internal communication channels to users within a care networkfor either or both providing post procedure care to a user and wellnessto the user, such as the internal messaging systems described in thispaper. The internal messaging system 410 can function to send andreceive care data through internal communication channels to userswithin a care network. Depending upon implementation-specific or otherconsiderations, the internal messaging system 410 can send postprocedure content and receive/forward care data in response to the postprocedure content. In sending care data through internal communicationchannels, the internal messaging system 410 can determine post procedurecontent to transmit according to care network data stored in the carenetwork datastore 406 and user specific care plan data stored in theuser specific care plan datastore 408. Additionally, in sending caredata through internal communication channels, the internal messagingsystem 410 can determine post procedure care conditions for transmittingcare data from care network data stored in the care network datastore406 and user specific care plan data stored in the user specific careplan datastore 408.

In the example system shown in FIG. 4, the internal messaging system 410includes a care network recipients determination engine 412, a careconditions determination engine 414, an internal messaging engine 416, amessaging datastore 418, and a care data receipt engine 420. In aspecific implementation, the care network recipient determination engine412 functions to determine care network recipients to care data to, inmaintaining and/or providing post procedure care to a user through acare network of the user. The care network recipients determinationengine 412 can determine recipients within a care network to receivecare data using care network data stored in the care network datastore406 and/or user specific care plan data stored in the user specific careplan datastore 408. Depending upon implementation-specific or otherconsiderations, the care network recipients determination engine 412 candetermine recipients of post procedure content. Further depending uponimplementation-specific or other considerations, the care networkrecipient determination engine 412 can determine recipients of care datareceived by the internal messaging system 410. For example if measuredvital statistics are received in response to a care alert, then the carenetwork recipients determination engine 412 can determine recipients towhich to transmit the received vital statistics.

In a specific implementation, the care conditions determination engine414 functions to determine post procedure care conditions associatedwith sending of care content. The care conditions determination engine414 can determine post procedure care conditions from user specific careplan data stored in the user specific care plan datastore 408. Dependingupon implementation-specific or other considerations, the careconditions determination engine 414 can determine post procedure careconditions for transmitting post procedure content to users within acare network. Further depending upon implementation-specific or otherconsiderations, the care conditions determination engine 414 candetermine post procedure care conditions for transmitting received caredata to users within a care network.

In a specific implementation, the internal messaging engine 416functions to transmit care data in providing and/or maintaining postprocedure care to a user through a care network of the user. Theinternal messaging engine 416 can transmit care data to recipientsdetermined by the care network recipients determination engine 412according to post procedure care conditions determine by the careconditions determination engine 414. Depending uponimplementation-specific or other considerations, the internal messagingengine 416 can transmit care data directly to one or a plurality ofusers. For example, the internal messaging engine 416 can transmit caredata directly to a plurality of users, thereby enabling group chatfunctionality. Further depending upon implementation-specific or otherconsiderations, the internal messaging engine 416 can transmit care databy posting the care data to a feed that is viewable by one or aplurality of users within a care network. Depending uponimplementation-specific or other considerations, a feed is viewable by aspecific subset of users within a care network.

In a specific implementation, the internal messaging engine 416functions to gain approval from a user before transmitting care datainternally. Depending upon implementation-specific or otherconsiderations, the internal messaging engine 416 can gain approval froma user before transmitting patient health information of the user. Forexample, the internal messaging engine 416 can gain approval fortransmitting measured vital statistics of a user before transmitting themeasured vital statistics. Further depending uponimplementation-specific or other considerations, in gaining approvalbefore transmitting care data internally, the internal messaging engine416 can transmit internally a message to a user requesting approval totransmit the care data. Depending upon implementation-specific or otherconsiderations, in gaining approval before transmitting care datainternally, the internal messaging engine 416 can instruct an externalmessaging system to transmit a message through an external communicationchannel to a user requesting approval. In gaining approval beforetransmitting care data internally, the internal messaging engine 416 canbe compliant with HIPAA standards.

In a specific implementation, the internal messaging engine 416functions to transmit care data with different indicia or color codingschemes. Depending upon implementation-specific or other considerations,the internal messaging engine 416 can determine indicia or a colorcoding scheme in which to transmit care data based on an originationsource of the care data, a recipient of the care data, the subject ofcare data, data included in care data, and/or post procedure careconditions. For example, if post procedure care conditions specify tocall out care data sent to a doctor if a blood pressure reading includedin care data is below a certain threshold, then the internal messagingengine 416 can mark a message sent to a doctor including the bloodpressure reading with an exclamation point. In another example, theinternal messaging engine 416 can mark all care data sent about aspecific patient with a certain color.

In a specific implementation, the messaging datastore 418 functions tostore messages and care data sent and/or received by the internalmessaging system 410. Depending upon implementation-specific or otherconsiderations, the messaging datastore 418 can store post procedurecontent sent by the internal messaging engine 416. Further dependingupon implementation-specific or other considerations, the messagingdatastore 418 can store care data received by the internal messagingsystem 410. The messaging datastore 418 can store transmission recordsof data sent and received by the internal messaging system. Transmissionrecords can include a source of care data, a recipient of care datatransmitted by the internal messaging system, and/or a time when thecare data was sent and/or received. Data stored in the messagingdatastore 418 can be stored as encrypted data at the file level, as incompliance with HIPAA standards. Further in compliance with HIPAAstandards, the messaging datastore 418 can be accessible through atleast two factor authentication. For example, the messaging datastore418 can be accessed through an SSL VPN implementing at least two factorauthentication. Depending upon implementation-specific or otherconfigurations, the messaging datastore 418 can be configured to notallow users to delete data from the messaging datastore 418, incompliance with HIPAA standards. For example, users can be restricted indeleting messages they receive through the internal messaging system410. Further depending upon implementation, specific or otherconsiderations, data stored in the messaging datastore 418 is backed upand saved for at least 6 years, further in compliance with HIPAAstandards.

In a specific implementation, the care data receipt engine 420 functionsto receive care data from users within a care network in providingand/or maintaining post procedure care. The care data receipt engine 420can receive care data from users within a care network in response topost procedure care content. The care data receipt engine 420 canprovide received care data to the internal messaging engine 416, wherethe received data can be transmitted in accordance with post procedurecare conditions to appropriate recipients within a care network.

In an example of operation of the example system shown in FIG. 4, thecare network recipients determination engine 412 determines recipientswithin a care network for receiving care data. In the example ofoperation of the example system shown in FIG. 4, the care conditionsdetermination engine determines post procedure care conditions forsending the care data. Further, in the example of operation of theexample system shown in FIG. 4, the internal messaging engine 416 sendsthe care data to the recipients according the post procedure careconditions. In the example of operation of the example system shown inFIG. 4, the messaging datastore 418 stores the transmitted care data.Additionally, in the example of operation of the example system shown inFIG. 4, the care data receipt engine 420 receives care data in responseto the transmitted care data. In the example of operation of the examplesystem shown in FIG. 4, the internal messaging engine 416 transmits thecare data received by the care data receipt engine 420 to appropriaterecipients within the care network according to post procedure careconditions.

FIG. 5 depicts a diagram 500 of an example of an external messagingsystem for providing and/or maintaining post procedure care for a userthrough a care network of the user. The example system shown in FIG. 5includes a computer-readable medium 502, user device 504-1 . . . 504-n(hereinafter referred to as “user devices 504”), a care networkdatastore 506, and an external messaging system 508. In the examplesystem shown in FIG. 5, the user devices 504, the care network datastore506, and the external messaging system 508 are coupled to each otherthrough the computer-readable medium 502.

In a specific implementation, the user devices 504 function according toan applicable user device for sending and/or receiving data used inproviding and/or maintaining post procedure care to a user through acare network of the user, such as the user devices described in thispaper. The user devices 504 can be associated with a user who is thesubject of a care network, and/or users within the care network of theuser. The user devices 504 can be used to receive care data receivednotifications. Depending upon implementation-specific or otherconsiderations, the user devices 504 can be thin client devices orultra-thin client devices. Further depending uponimplementation-specific or other considerations, the user devices 504can include wireless or cellular network interfaces through which theuser devices 504 can be wirelessly connected to the computer-readablemedium 502.

In a specific implementation, the care network datastore 506 functionsaccording to an applicable datastore for storing care network data, suchas the care network datastores described in this paper. Care networkdata stored in the care network datastore 506 can include data about acare network of a specific user. Depending upon implementation-specificor other considerations, care network data stored in the care networkdatastore 506 can include an identification of users within a carenetwork, what care data can be sent to which users within the carenetwork in accordance with satisfaction of post procedure careconditions for the care data, and/or external communication channelsthrough which users can receive data.

In a specific implementation, the external messaging system 508functions to send messages through an external communication channel tousers within a care network for providing and/or maintaining postprocedure care to a user. The external messaging system 508 can sendcare data received notifications. In sending messages through anexternal communication channel, the external messaging system 508 candetermine whether an account associated with a user has received caredata through an internal messaging system. Further, the externalmessaging system 508 can determine external communication channels tosend messages to users through, and subsequently send messages throughthe determined external communication channels to the users.

In the example system shown in FIG. 5, the external messaging system 508includes a care data received determination engine 510 and an externalmessaging engine 512. In a specific implementation, the care datareceived determination engine 510 functions to determine if an accounthas received care data through an internal messaging system. Dependingupon implementation-specific or other considerations, the care datareceived determination engine 510 can determine if an account hasreceived care data through an internal messaging system in real time asthe care data is sent to the account. Further depending uponimplementation-specific or other considerations, the care data receiveddetermination engine 510 can determined an account has received caredata based on a notification from the internal messaging system. Thecare data received determination engine can determine a user associatedwith an account through care network data stored in the care networkdatastore 506.

In a specific implementation, the external messaging engine 512functions to send a notification over an external communication channelindicating that the user has received care data through an internalmessaging system. The external messaging engine 512 can send care datareceived notifications based on a determination of a user associatedwith an account that has received care data through an internalmessaging system, as determined by the care data received determinationengine 510. Depending upon implementation-specific or otherconsiderations, the external messaging engine 512 can determine apreferred external communication channel from care network data storedin the care network datastore 506 and subsequently send notification tothe users over the preferred external communication channels. Examplesof external communication channels through which the external messagingengine 512 can send notifications are text and/or email. Notificationssent by the external messaging engine are generic in that they do notcontain any patient health information and are therefore in compliancewith HIPAA.

In an example of operation of the example system shown in FIG. 5, thecare data received determination engine 510 determines a user associatedwith an account that has received care data through an internalcommunication system. In the example of operation of the example systemshown in FIG. 5, the external messaging engine 512 determines apreferred communication channel of the user determined by the care datareceived determination engine 510. Further, in the example of operationof the example system shown in FIG. 5, the external messaging engine 512sends a care data received notification to the user through thepreferred communication channel of the user.

FIG. 6 depicts a diagram 600 of a post procedure analytics managementsystem. The example system shown in FIG. 6 includes an analytics datacollection engine 602 and an analytics report generation engine 604.

In a specific implementation, the analytics data collection engine 602functions to collect analytics data based on providing and/ormaintaining post procedure care to a user through a care network.Analytics data can include actions that are taken by users in a carenetwork in providing post procedure care, usage analytics of users in acare network, and/or care analytics of providing post procedure care toa user through a care network. Care analytics can include the type ofcare data that was transmitted internally, which users provided caredata, and/or which user received care data.

In a specific implementation, the analytics report generation engine 604functions to generate an analytics report based on analytics datacollected by the analytics data collection engine 602. The analyticsreport generation engine 604 can generate an analytics report for eachtype of analytics data or a report with combined different types ofanalytics data. Depending upon implementation-specific or otherconsiderations, the analytics report generation engine 604 can send theanalytics report to users within a care network, or otherwise make theanalytics report viewable to eth users within the care network. Userswithin a care network can use an analytics report to improve postprocedure care and/or provide coaching to users within the care network.

FIG. 7 depicts a diagram 700 of an example of a system for sendingmessages internally between users in a care network in providing and/ormaintaining post procedure care. The example system shown in FIG. 7includes a computer-readable medium 702, a user device 704, and a userwellness management system 706. In the example system shown in FIG. 7,the user device 704 and the user wellness management system 706 arecoupled to each other through the computer-readable medium 702.

In a specific implementation, the user device 704 functions according toan applicable device for sending and receiving wellness data used inproviding wellness to a user through a wellness network, such as theuser devices described in this paper. The user device 704 can send andreceive data to and from the user wellness management system through anapplicable system for sending and receiving data through internalcommunication channels, such as the internal messaging systems describedin this paper.

In a specific implementation, the user wellness management system 706functions to provide wellness to a user through a wellness network. Awellness network can include a plurality of users that are chosen by auser who is the subject of the wellness network. Depending uponimplementation-specific or other considerations, the user wellnessmanagement system 706 can perform a health risk assessment of a user.Further depending upon implementation-specific or other considerations,the user wellness management system 706 can track activities of a userand challenge the user to perform certain activities to improve thewellness of the user.

In the example system shown in FIG. 7, the user wellness managementsystem 706 includes a wellness network management engine 708, a wellnessnetwork datastore 710, a health risk assessment engine 712, a healthrisk assessment datastore 714, an activity logging engine 716, and achallenge engine 718. In a specific implementation, the wellness networkmanagement engine 708 functions to manage a wellness of a user. Inmanaging a wellness network of a user, the wellness network managementengine 708 can add and/or remove users from a wellness network. Exampleof users that can be in a wellness network include family members and/orlifestyle coaches. Users within a wellness network can communicationthrough an applicable internal messaging system, such as the internalmessaging systems described in this paper.

In a specific implementation, the wellness network datastore 710functions to store wellness network data indicating a wellness networkof a user. Wellness network data can indicate users within a wellnessnetwork and ways in which the users can be contacted. Wellness networkdata stored in the wellness network datastore 710 can be generatedand/or modified by the wellness network management engine 708. Wellnessnetwork data stored in the wellness network datastore 710 can be storedas encrypted data at the file level, as in compliance with HIPAAstandards. Further in compliance with HIPAA standards, the wellnessnetwork datastore 710 can be accessible through at least two factorauthentication. For example, the wellness network datastore 710 can beaccessed through an SSL VPN implementing at least two factorauthentication.

In a specific implementation, the health risk assessment engine 712functions to perform a health risk assessment on a user who is thesubject of a wellness network. A health risk assessment can includepotential health risks to a user. The health risk assessment engine 712can perform a health risk by presenting questions and based on a user'sanswer to those questions, generate a health risk assessment. Examplesof questions that the health risk assessment engine 712 can present to auser include, how often a user exercises, what a user's diet includes,and whether a user smokes. The health risk assessment engine 712 canstore a health risk assessment for a user as health risk assessment datain the health risk assessment datastore 714. Depending uponimplementation-specific or other considerations, the health riskassessment engine 712 can perform a health risk assessment on a user,once or a plurality of times throughout the life of a user.

In a specific implementation, the activity logging engine 716 functionsto log activities of a user in providing wellness to a user. Theactivity logging engine 716 can log activities related to diet,exercise, and daily occurrences of a user. Depending uponimplementation-specific or other considerations, the activity loggingengine 716 can determine activities to log by asking questions for auser. For example, the activity logging engine 716 can ask a user ifthey exercised on a specific day. Further depending uponimplementation-specific or other considerations, the activity loggingengine 716 can determine activities to log from data received from awearable device of a user, an application, and/or a service, such as thewearable devices, applications, and services previously described.Depending upon implementation-specific or other considerations, theactivity logging engine 716 can generate a wellness report of loggedactivities that a user can view to improve their wellness. Furtherdepending upon implementation-specific or other considerations, wellnesspoints can be awarded based on the performance of certain activitieslogged by the activity logging engine 716. Wellness points can be usedto redeem gifts or obtain rewards, e.g. a gift card.

In a specific implementation, the challenge engine 718 functions topresent challenges to a user, that the user can perform to improve theirwellness. Depending upon implementation-specific or otherconsiderations, the challenge engine 718 can present challenges based onspecific health risks to a user, as identified in a health riskassessment. Further depending upon implementation-specific or otherconsiderations, the challenge engine 718 can present a challenge createdby another user, e.g. a wellness coach. Challenges can includeassociated wellness points that can be awarded to a user aftercompletion of a challenge or a portion of a challenge.

In an example of operation of the example system shown in FIG. 7, thewellness network management engine 708 manages a wellness network of auser. In the example of operation of the example system shown in FIG. 7,the health risk assessment engine generates a health risk assessment forthe user. Further, in the example of operation of the example systemshown in FIG. 7, the activity logging engine logs activities of a userfor use in monitoring wellness of the user. In the example of operationof the example system shown in FIG. 7, the challenge engine 718 presentschallenges to the user that can improve the wellness of the user if theyare performed.

FIG. 8 depicts a flowchart 800 of an example of a method for providingand/or maintaining post procedure care to a user through a care networkof the user. The flowchart 802 begins at module 802, where a carenetwork of a user is formed. A care network of a user can include familymembers who will provide care to a user and/or doctors who performed aprocedure on the user. A care network of a user can be formed by a postprocedure care network management engine.

The flowchart 800 continues to module 804 where a care plan is formedfor a user. A care plan can include post procedure content to send tothe user or other users within the care network and post procedure careconditions that must be met in order to send the post procedure carecontent. Depending upon implementation-specific or other considerations,post procedure content included in the care plan can include carealerts. Further depending upon implementation-specific or otherconsiderations, the care plan can be formed either with or without theaid of a customizable care plan template. The care plan can be formed bya user specific care plan management engine.

The flowchart 800 continues to decision point 806 where it is determinedif the post procedure care conditions have been met. If it is determinedthat the post procedure care conditions are met, then the flowchart 800continues to module 808. At module 808, the post procedure care contentis sent to the user through an internal communication channel. Aninternal messaging engine can send the post procedure content through aninternal communication channel. Depending upon implementation-specificor other considerations, the post procedure content can be sent directlyto an account associated with the user or posted on a feed that the usercan view.

The flowchart 800 continues to module 810, where a care data receivednotification is sent to the user through an external communicationchannel. Depending upon implementation-specific or other considerations,an external communication channel can be a preferred externalcommunication channel of the user. An external messaging engine can sendthe care data received notification to the user through an externalcommunication channel. A care data received notification sent throughthe external communication channel can be generic in that it does notcontain any personal health information of the user.

The flowchart 800 continues to module 812, where the user is logged into access the post procedure content sent through the internalcommunication channel. In logging in the user, user credentials for theuser can be received and then authenticated in order to login the user.Depending upon implementation-specific or other considerations, the usercan remain logged in until a certain period of inactivity occurs, afterwhich the user will be logged out. A user login engine can manage thelogging in and logging out of the user.

FIG. 9 depicts a flowchart 900 of an example of a method for sendingcare data in a care network of a user for providing and/or maintainingpost procedure care to the user through the care network of the user.The flowchart 900 begins at module 902, where care data is received froma user with a care network through an internal communication channel.Care data received at module 902 can be generated in response to postprocedure content sent to the user. For example, care data can bemeasured vital statistics of the user in response to post procedurecontent that is a care alert reminding the user to take their vitalstatistics. The care data can be received by a care data receipt engine.

The flowchart 900 continues to module 904, where an appropriaterecipient for the care data in the care network is determined. Anappropriate recipient for the care data can be determined by a carenetwork recipients determination engine. An appropriate recipient can bedetermined based on care network data for the care network and/or userspecific care plan data for the user. Additionally, at module 904, postprocedure care conditions can be determined for the care data. Postprocedure care conditions can be determined by a care conditionsdetermination engine.

The flowchart 900 continues to decision point 906, where it isdetermined whether the post procedure care conditions are met. If it isdetermined that the post procedure care conditions are met, then theflowchart 900 continues to decision point 908. At decision point 908 itis determined whether the user has given approval to transmit the caredata.

If it is determined that the user has given approval to transmit thecare data, then the flowchart 900 continues to module 910. At module910, the care data is sent to the recipient through an internalcommunication channel. An internal messaging engine can send the caredata through an internal communication channel. Depending uponimplementation-specific or other considerations, the care data can besent directly to an account associated with the recipient or posted on afeed that the recipient can view.

The flowchart 900 continues to module 912, where a care data receivednotification is sent to the recipient through an external communicationchannel. Depending upon implementation-specific or other considerations,an external communication channel can be a preferred externalcommunication channel of the recipient. An external messaging engine cansend the care data received notification to the recipient through anexternal communication channel. A care data received notification sentthrough the external communication channel can be generic in that itdoes not contain any personal health information of the recipient.

The flowchart 900 continues to module 912, where the recipient is loggedin to access the care data sent through the internal communicationchannel. In logging in the recipient, user credentials for the recipientcan be received and then authenticated in order to login the recipient.Depending upon implementation-specific or other considerations, therecipient can remain logged in until a certain period of inactivityoccurs, after which the recipient will be logged out. A user loginengine can manage the logging in and logging out of the recipient.

FIG. 10 depicts a flowchart 1000 of an example of a method forgenerating a user specific care plan for providing and/or maintainingpost procedure care of a user through a care network of the user. Theflowchart 1000 begins at module 1002 where post procedure content andassociated post procedure conditions are received. Post procedurecontent and associated post procedure conditions can be received by acare content retrieval engine. Depending upon implementation-specific orother considerations, post procedure content and associated postprocedure conditions can be received from a third party source, a careprovider, and/or a doctor who performed the procedure.

The flowchart 1000 continues to module 1004 where a customizable careplan template is generating using the post procedure content andassociated post procedure care conditions. A customizable care plantemplate can be specific to a type of procedure and/or a doctor whoperformed a procedure. A customizable care plan template can begenerated by a customizable care plan template management engine.

The flowchart 1000 continues to module 1006 where the customizable carepan template is sent to a user in a care network of the user. Theanother user in the care network of the user can be a doctor whoperformed the procedure and/or a care giver. The customizable care plantemplate can be sent through an internal communication channel by thecustomizable care plan template management engine.

The flowchart 1000 continues to module 1008 where customized care plandata is received from the another user based on the customizable careplan template. The customized care plan data can be received through aninternal communication channel. A user specific care plan managementengine can receive the customized care plan data.

The flowchart 1000 continues to module 1010 where a user specific careplan is generated for the user based on the customized care plan data. Auser specific care plan management engine can generate the user specificcare plan. A user specific care plan can include care data, includingpost procedure content and associated post procedure care conditions,for providing and/or maintaining post procedure care to the user.

FIG. 11 depicts a flowchart 1100 of an example of a method for providingand/or maintaining wellness for a user. The flowchart 1100 begins atmodule 1102 where a wellness network is formed for a user. A wellnessnetwork can include family members and coaches for promoting wellnessfor a user. A wellness network management engine can form a wellnessnetwork for a user based on instructions received from the userindicating parties that the user wants in their wellness network.

The flowchart 1100 continues to module 1104 where a health riskassessment is performed for the user. A health risk assessment can beperformed by presenting questions to the user and forming the assessmentbased on the answers to the questions provided by the user. A healthrisk assessment can be performed by a health risk assessment engine.

The flowchart 1100 continues to module 1106 where activities related tothe wellness of the user are logged. Activities related to the wellnessof the user can include exercise activities and dietary activities. Anactivity logging engine can log the activities related to the wellnessof the user. Depending upon implementation-specific or otherconsiderations, the log of the activities can be presented to a user forcoaching the user in wellness.

The flowchart 1100 continues to module 1108, where a challenge ispresented to the user to improve their wellness based on the health riskassessment and/or users in the wellness network. For example, a coach inthe wellness network can suggest a challenge that a user shouldundertake. In another example, a challenge that a user should undertakecan be determined based on particular health risks of the user indicatedby the health risk assessment.

FIG. 12 depicts an example of a screenshot 1200 of an interface used tolog in to an internal communication channel. The interface includesfields in which user credentials can be entered and used to access caredata sent through an internal messaging system.

FIG. 13 depicts an example of a screenshot 1300 of an interface for usein managing post procedure care of users in care networks. The interfaceincludes tabs through which a user can view info about users within acare network. The interface also includes tabs through which a user canactivate to transmit care data used in managing and/or providing postprocedure care data to a user.

FIG. 14 depicts an example of a screenshot 1400 of another example of aninterface for use in managing post procedure care of users in carenetworks. The interface includes contact information of patient. Theinterface also includes messages including care data sent to thepatients.

These and other examples provided in this paper are intended toillustrate but not necessarily to limit the described implementation. Asused herein, the term “implementation” means an implementation thatserves to illustrate by way of example but not limitation. Thetechniques described in the preceding text and figures can be mixed andmatched as circumstances demand to produce alternative implementations.

We claim:
 1. A method comprising: generating a care network for a carerecipient in providing post procedure care to the care recipient for aprocedure performed on the care recipient; generating a user specificcare plan for the care recipient, the user specific care plan includingpost procedure content and first post procedure care conditionsassociated with the post procedure content; determining if the firstpost procedure care conditions are satisfied; if it is determined thatthe first post procedure care conditions are satisfied: sending the postprocedure content to the care recipient through an internalcommunication channel; sending a first care data received notificationto the care recipient through an external communication channel, thefirst care data received notification being a generic notificationlacking any personal health information of the care recipient; loggingin the care recipient to view the post procedure content through theinternal communication channel.
 2. The method of claim 1, furthercomprising: generating a customizable care plan template for theprocedure; sending the customizable care plan to a user within the carenetwork for the care recipient; receiving customized care plan data fromthe user in response to the customizable care plan template; generatingthe user specific care plan based on the customizable care plantemplate.
 3. The method of claim 1, wherein the external communicationchannel is a short message service communication channel, and the caredata received notification is sent as a push notification.
 4. The methodof claim 1, further comprising: receiving care data from the carerecipient through the internal communication channel in response to thepost procedure content; determining a user in the care network of thecare recipient to send the care data to; determining if the carerecipient approves sending of the care data to the user; if it isdetermined that the care recipient approves sending of the care data tothe user: sending the care data to the user through the internalcommunication channel; sending a second care data received notificationto the user through the external communication channel, the second caredata received notification being a generic notification lacking anypersonal health information of the care recipient; logging in the userto view the care data through the internal communication channel.
 5. Themethod of claim 4, wherein the care data includes health measurements ofthe care recipient, the health measurement of the care recipient takenby a wearable device of the care recipient.
 6. The method of claim 1,further comprising: determining if the care recipient has been logged into view the post procedure content with inactivity for a specific amountof time; if it is determined that the care recipient has been logged into view the post procedure content with inactivity for a specific amountof time, logging out the care recipient from viewing the post procedurecontent.
 7. The method of claim 1, wherein the post procedure content issent through the internal communication channel directly to an accountassociated with a care recipient.
 8. The method of claim 1, wherein thepost procedure content is posted on a feed that the care recipient canview through the internal communication channel.
 9. The method of claim4, further comprising: determining the user from care network data andthe user specific care plan; determining second post procedure careconditions for the care data; sending the care data to the user throughthe internal communication channel if the second post procedure careconditions are met.
 10. The method of claim 4, wherein the user is adoctor who performed the procedure on the care recipient.
 11. A systemcomprising: a post procedure care network management engine configuredto generate a care network for a care recipient in providing postprocedure care to the care recipient for a procedure performed on thecare recipient; a user specific care plan management engine configuredto generate a user specific care plan for the care recipient, the userspecific care plan including post procedure content and first postprocedure care conditions associated with the post procedure content; acare condition determination engine configured to determine if the firstpost procedure care conditions are satisfied; an internal messagingengine configured to send the post procedure content to the carerecipient through an internal communication channel, if it is determinedthat the first post procedure care conditions are satisfied; an externalmessaging engine configured to send a first care data receivednotification to the care recipient through an external communicationchannel, the first care data received notification being a genericnotification lacking any personal health information of the carerecipient, if it is determined that the first post procedure careconditions are satisfied; a user login engine configured to log in thecare recipient to view the post procedure content through the internalcommunication channel.
 12. The system of claim 11, further comprising: acustomizable care plan template management engine configured to:generate a customizable care plan template for the procedure; send thecustomizable care plan to a user within the care network for the carerecipient; a user specific care plan management engine configured to:receive customized care plan data from the user in response to thecustomizable care plan template; generate the user specific care planbased on the customizable care plan template.
 13. The system of claim11, wherein the external communication channel is a short messageservice communication channel, and the care data received notificationis sent as a push notification.
 14. The system of claim 11, furthercomprising: a care data receipt engine configured to receive care datafrom the care recipient through the internal communication channel inresponse to the post procedure content; a care network recipientsdetermination engine configured to determine a user in the care networkof the care recipient to send the care data to; the internal messagingengine further configured to: determine if the care recipient approvessending of the care data to the user; send the care data to the userthrough the internal communication channel, if it is determined that thecare recipient approves sending of the care data to the user; theexternal messaging engine further configured to send a second care datareceived notification to the user through the external communicationchannel if it is determined that the care recipient approves sending ofthe care data to the user, the second care data received notificationbeing a generic notification lacking any personal health information ofthe care recipient; the user login engine further configured to log inthe user to view the care data through the internal communicationchannel.
 15. The system of claim 14, wherein the care data includeshealth measurements of the care recipient, the health measurement of thecare recipient taken by a wearable device of the care recipient.
 16. Thesystem of claim 11, wherein the user login engine is further configuredto: determine if the care recipient has been logged in to view the postprocedure content with inactivity for a specific amount of time; if itis determined that the care recipient has been logged in to view thepost procedure content with inactivity for a specific amount of time,the user login engine logging out the care recipient from viewing thepost procedure content.
 17. The system of claim 11, wherein the internalmessaging engine is configured to send the post procedure contentthrough the internal communication channel directly to an accountassociated with a care recipient.
 18. The system of claim 11, whereinthe internal messaging engine is configured to post the post procedurecontent on a feed that the care recipient can view through the internalcommunication channel.
 19. The system of claim 14, further comprising: acare network recipients determination engine configured to determine theuser from care network data and the user specific care plan; a careconditions determination engine configured to determine second postprocedure care conditions for the care data; the internal messagingengine further configured to send the care data to the user through theinternal communication channel if the second post procedure careconditions are met.
 20. A system comprising: a means for generating acare network for a care recipient in providing post procedure care tothe care recipient for a procedure performed on the care recipient; ameans for generating a user specific care plan for the care recipient,the user specific care plan including post procedure content and firstpost procedure care conditions associated with the post procedurecontent; a means for determining if the first post procedure careconditions are satisfied; a means for sending the post procedure contentto the care recipient through an internal communication channel, if itis determined that the first post procedure care conditions aresatisfied; a means for sending a first care data received notificationto the care recipient through an external communication channel, thefirst care data received notification being a generic notificationlacking any personal health information of the care recipient; a meansfor logging in the care recipient to view the post procedure contentthrough the internal communication channel.